|
The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included. |
Business-critical functions may include but are not limited to: | financial systemscustomer service functionspayroll |
Documentation may follow: | ISO/IEC/AS standardsaudit trailsnaming standardsversion controlproject management templates and report writingmaintaining equipment inventoryclient trainingsatisfaction reports |
Project team may include: | solution developers and business clients working togetherindividual business analystsa number of third-party solution developers working togethera number of different businesses working in partnership |
Software may include but are not limited to: | commercialin-housepackaged or customised software |
Specifications may include but are not limited to: | technical requirementsuser problem statementcurrent system functionality |
Constraints may include but are not limited to: | timebudgetresourcehardwaresoftwarepolicylegal constraints |
System may include but are not limited to: | databasesapplicationsserversoperating systemsgatewaysapplication service providerISP |
Appropriate person may include: | supervisorteacherauthorised business representativeclient |
Threats may include: | Weather (storms, earthquake)SecurityInformation technology failure (hardware, software)AccidentEspionageSabotage (hackers)Telecommunications network failureDenial of serviceVirus attackSupplementary questioning of the client may be used during the assessment phase, where necessary, to ensure that all issues relating to threats to the system are considered and appropriate choices made given the need to prevent, limit, recover, respond and recover from disasters |
Back-up strategy may include: | hot standby sitewarm standby sitecold standby sitemobile vansupplierbureaucontacts through user groupthird parties |
Contingency plans will vary in format and content detail, but will typically: | identify weaknesses and provide for the implementation of a disaster prevention programminimise disruption to business operationsprovide a coordinated approach to the disaster recovery process |
Cut-over criteria may include: | estimate of time before system is operationalestimate of business impactauthorisations to cut-overactual system down timerefresher of cut-over plan |
Security environment | Includes legislation, organisational security policies, customs, expertise and knowledge that are, or may be, relevant. The security environment also includes the threats to security that are, or are held to be, present in the environment |
Statutory requirements | May include legislation (e.g. Privacy Act), industry-imposed controls and standards. In certain organisations (e.g. health and banking), there may be strict laws regarding confidentiality and reporting of data |
Commercial requirements | Back-upStorage and recovery of dataAccess to internal networkPasswords/logonsEncryptionFirewallsHackingConfidentialityIntegrityAvailability |
Standards may include: | ISO/IEC/AS standardsorganisational standardsproject standards (for further information refer to the Standards Australia website at: www.standards.com.au ) |